home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Archive Magazine CD 1995
/
Archive Magazine CD 1995.iso
/
discs
/
pipeline
/
abacus
/
p_line
/
CmdFile1
/
ReadMe
Wrap
Text File
|
1992-02-02
|
2KB
|
44 lines
%OP%VS4.12 (10-Feb-92), Gerald Fitton, R4000 2915 6625 6368
%OP%DP0
%OP%IRY
%OP%PL0
%OP%HM0
%OP%FM0
%OP%BM0
%OP%LM4
%OP%PT1
%OP%PDPipeLine
%OP%WC802,2070,344,1620,0,0,0,0
%CO:A,72,72%
%C%Running Command Files
%C%by Gerald L Fitton
Keywords:
Command Macros Fitton
What were called 'Macros' in PipeDream 3 are called PipeDream Command
Files in PipeDream 4. Michael Genever-Watling and others complain that
often command files (macros) which load a file fail to run when the
command file has been copied to a new disc or directory.
Michael says "I have a problem with your Macro files which may be a bug
in my version. I cannot run your Macros by double clicking on the Icon
since all I get when I do is a "Can't find file ÿ" error (note that "y"
is actually a y with double dot over it!). I can however run them
using the keyboard command <Ctrl FZ>. If this isn't a bug can you
advise what the problem is?"
Well Michael, the problem is that the full path name in the command
file does not correspond exactly to the correct full path name to the
wanted file.
If you send me an application which includes a file loading (or saving)
macro then I put it on one of the PipeLine discs the chances are that
my PipeLine disc name will be different from the disc name you have
used. The result is that the path name is different and the command
file fails to find the path!
If you can work out a way around this problem then many of us would
like to know the solution. I thought I had something using a
*Set Macro$Dir command but I am afraid I lost it when my hard disc died
in December 1991 and I can't remember how to reconstruct it!
%CO:B,12,0%%CO:C,12,0%%CO:D,12,0%%CO:E,12,0%